An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi all, Like others my app submission has been stuck in “waiting for review” for weeks. I know initial app reviews take longer than updates, but this has been delayed far too long and makes me concerned about repeating the process in the future. I submitted this app for review back on Feb 10. It was initially rejected for a minor issue, which I resolved and resubmitted the same day. After that, the build remained in “Waiting for Review” for about two weeks with no further communication. At that point I canceled the submission and resubmitted the build, thinking it may have been stuck in the queue (I now know not to do this next time). Unfortunately the new submission has also been waiting for review for another 9 days now with no messages or updates. I’ve contacted app review support as well (case ID- 102826632729). I understand review times can vary, but delays like this make it difficult for developers to plan launches or push updates when the review process is the only path to distributing apps. As paying members of the Apple Developer Program, we rely heavily on this pipeline functioning reliably. Hoping this post will reach someone from Apple who can help move the process along. If any other devs have suggestions/tips that have worked for them, please share so others in this position can become unblocked. Thanks in advance.

Hi App Review team, This is my first app submission. SiteLog AI (Apple ID 6768819001), version 1.0, build 56, has been in "Waiting for Review" since August 1, 2026 — about 10 days. The App Review page in App Store Connect shows no messages, no rejection, and no outstanding items, so nothing appears to be needed from me. My developer membership and agreements are active, and the app is not distributed in the EU (DSA declared non-trader). Could someone confirm the submission is queued as expected, and whether anything is needed from me to proceed? Happy to provide any additional detail. Thank you.

Hi everyone, First, some context and a genuine compliment: this is our first iOS submission, and overall the App Store Connect tooling and TestFlight have been a great experience — our beta reached 1,351 external testers organically, with 1,700+ sessions and a crash rate below 1%. That said, we're stuck in a loop we don't know how to break, and I'd love advice from anyone who has been through it. Our game, Truckers Brasil Online, is a truck simulator with proprietary real-time online multiplayer, 100% developed in-house in Unity by our Brazilian studio. Same game, same brand and same company operating on Google Play since 2024. Our official YouTube channel has 1.84M subscribers with years of public devlogs documenting the development. We own all source code, all 3D models (including the original Blender source files of every truck), and the dedicated servers that run the multiplayer. The review history: Jul 04 — rejected under 4.3(a) Spam ("similar binary, metadata, and/or concept"), no specific app named Jul 05 — we replied with a detailed originality dossier (PDF attached to the conversation) Jul 14 — next review did NOT raise 4.3(a); it moved to a connection bug and gameplay questions, which we fully answered with a corrected build and a step-by-step visual guide Aug 07 — the same generic 4.3(a) text returned, with no new facts and no reference to any of the evidence Each of the three reviews lasted under 20 minutes according to the activity log, so we suspect the attached evidence was never actually opened. We have already: replied in the conversation with a complete evidence dossier, filed a formal appeal to the App Review Board, and contacted Developer Support (case open). Questions for the community: Has anyone successfully overturned a repeated 4.3(a) on a genuinely original game? What ended up working? Is there anything else we can do while the appeal is pending — or anything we should avoid doing? For Unity games specifically: is there any known way to reduce false-positive binary similarity flags? We're happy to provide any verification — source code, Blender files, live server access, video demo. We just need the evidence to actually be looked at. Thanks in advance for any guidance! Thiago — LTDA VERA CRUZ (FG Games Entertainment)

Hello, I’m looking for guidance regarding an unusually long App Review process for my app, Auto Deal. The app was originally submitted on July 2, 2026. It eventually entered “In Review,” but remained there for an unusually long period without any update or decision. After waiting for a long time with no progress, I deleted the submission and uploaded it again. On the second submission, we again experienced a long delay. The app was eventually reviewed and rejected because of an issue that occurred when tapping the “Confirm” button inside the app. I immediately fixed the exact issue identified by App Review and submitted the corrected build. The corrected submission then entered “In Review,” but once again remained there for a long period without any further feedback or decision. After waiting again with no progress, I deleted the submission and uploaded a new build. When the same prolonged delay continued, I deleted that submission and submitted another fresh build. I understand that deleting and resubmitting can restart the review process. However, I only took these steps after repeatedly experiencing unusually long periods in review without any decision or explanation. Throughout this entire process, I have contacted Apple Developer Support multiple times and submitted three expedited review requests, but the issue remains unresolved. The app is complete and already available on Google Play. We have customers waiting for the iOS version, and this prolonged review process has significantly delayed our business launch. I am not requesting another expedited review through this post. I am trying to understand why this keeps happening and whether there is an issue with the app submission, my developer account, or the review process that requires action from my side. If an Apple engineer or App Review representative can look into this situation or advise me on the appropriate next step, I would greatly appreciate it. Thank you.

Hello App Review team, Our first submission has been in "Waiting for Review" for nine days and has never entered "In Review." There are no messages in Resolution Center and no requests for additional information. App name: Farm Tech Ready Apple ID: 6796078026 Platform: iOS Version / Build: 1.0 Submitted: August 3, 2026 at 1:16 PM Status inquiry filed via Contact Us: August 10, 2026 This is a free educational self-assessment tool published under a University of Wisconsin-Madison team account for agricultural producers. No user accounts, no data collection, no in-app purchases. Could someone confirm whether this submission is queued correctly or whether something is blocking it from entering review? Thank you.

Has anyone else been experiencing unusually long app submission review times?We submitted our app for review almost a week ago (6 days) and the status is still "waiting for review". It's never taken this long before. Wondering if anyone else is experiencing unusally long wait times due to their review team being backed up, or if something unusual is up with our app...

Hi Apple Developer Community, I’m preparing an iOS app called Titech for App Review. The app is intended for clinic/business users and provides preliminary AI-generated cosmetic analysis and preview guidance based on user-submitted face photos. The app is not intended to provide medical advice, diagnosis, or treatment decisions, and users are told to consult qualified experts before acting on any recommendation. We have received multiple App Review rejections and I would appreciate guidance on whether our current approach is aligned with Apple’s expectations. Current issues raised by App Review: Guideline 2.1 - Information Needed Apple asked for more information about how the app uses face data, including: What face data is collected How it is used, stored, retained, deleted, and shared Whether it is shared with third parties Where this is explained in the privacy policy Exact privacy policy text about face data We updated the app and privacy policy to explain that: Users voluntarily upload front, left-side, and right-side face photos Photos may be sent to our backend and processed by OpenAI through the OpenAI API Face ID/fingerprint data is not collected Uploaded face photos and generated preview images are deleted after the active session ends The app does not sell face data or share it with advertisers/data brokers Guideline 2.1(b) - Information Needed Apple asked about the business model and whether users access paid content. Our app does not currently include paid digital content, subscriptions, credits, or in-app purchases. Access is controlled by a registration code for clinic/business users and App Review only. Guideline 2.3.3 - Accurate Metadata Apple said the screenshots did not show the current version of the app in use. We replaced the screenshots with updated iPhone and iPad screenshots showing: Clinic access Consent and face-data disclosure Photo capture AI-generated analysis Recommendations Side effects page Generated preview flow My questions: For apps using user-submitted face photos with a third-party AI API, is it enough to clearly disclose OpenAI processing in the consent screen and privacy policy, or should this also be repeated elsewhere in the app flow? For face photos that are deleted after the active session ends, what wording does Apple generally expect around retention and deletion? Since the app is clinic/business access only and does not sell digital content, is a registration code acceptable if we clearly explain that it is not a paid digital unlock? Are there any additional App Review notes or privacy policy sections that developers usually include for apps involving face photos and AI-generated preliminary recommendations? For metadata, should the screenshots avoid login/consent screens entirely, or is it acceptable to include them as long as most screenshots show core app functionality? Any advice from developers who have passed review with apps involving user-uploaded face photos, AI analysis, or cosmetic/health-adjacent recommendations would be very helpful. Thank you.

Hi Everyone, I really hate to be that guy but I was wondering if anyone else has been waiting as long as I have to get their app reviewed? I have an app that I put up for review July 30th and now we're on the 12th day waiting. (By the way, if you are an apple employee and you happen to see this message and want to help, the app is called Sudoku Every Day - Paper & Pen and the submission ID is f6750769-9018-4236-b413-ea07bc05d907). I know they are experiencing a backlog right now, and I've been patient understanding that. I guess I'm just a little frustrated because I see people on social media who supposedly put their app in after me that have already been approved, although I get that that's just random luck of the draw probably. Do you all think it's possible my app is stuck though? Should I request an expedited review? I kind of don't want to do that just because I bet everyone is doing that with the backlog and I don't believe I qualify for it. I do have a big update ready since I've added a lot of variants to my app in the last few weeks. That's ready to go but that's not really time critical ..... Another thing I was wondering is could this have something to do with the fact that I first tried to submit it after building in Xcode 27 beta? The beta builds kept getting auto-rejected so I had to eventually submit a build that I made on another computer (MacOS 26.6/Xcode 26.6) to get it to be accepted into review but that was the 6th build. Is there a chance my previous builds getting auto-rejected put me on some slow train to app review? Just curious to hear others experiences. If you made it all the way to the end of this, thanks for reading! -E

Hello, My app (App ID: 6797305708) was submitted on August 3, 2026, and has been in "[Waiting for Review / In Review]" status for over 9 days with no movement. I understand review times are longer than usual right now, but this is well beyond the typical turnaround. I have made two attempts to contact Apple about this: There are no messages or requests for additional information from the review team in App Store Connect, and I've confirmed the submission is complete with no pending actions on my end. Could someone from the App Review team please check on the status of this submission? If there's an issue I can address to move things forward, I'd be glad to fix it — I just need some communication about what's happening. Thank you.

We submitted our first iOS app for review on August 4, 2026 (App ID: 6797034989). Today is August 12, and it has now been 8 days in “Waiting for Review”. Apple’s submission confirmation stated that 50% of apps are reviewed within 24 hours and over 90% within 48 hours. We understand that delays can happen, but 8 days is significantly longer than expected. Since August 8, we have also sent 3 emails to Developer Support regarding this issue, but unfortunately received no response. We have deadlines for our app launch and cannot keep waiting indefinitely without any information. Could someone from App Review or Developer Support please take a look at our submission and let us know if everything is OK? We would really appreciate it if the review could begin as soon as possible. Thank you.

My app store review submission has sat in Waiting for Review for 8 days and has never moved to In Review. Checked and confirmed: Free Apps Agreement active Nothing in Resolution Center No contact from App Review at any point Reviewer demo account verified working end to end against production No builds removed or resubmitted since the original submission Developer Support case 20000132574764 was filed 8 August. No response so far. Is anyone else seeing new-app submissions failing to enter the queue in August? Any guidance on escalating this would be appreciated.

Hello App Review Team, Our iOS app has been stuck in "Waiting for Review" for more than 12 days with no status change and no Resolution Center messages. App name: Express Evaluations Developer: Express Evaluations, Inc Platform: iOS Version: 1.0 Current status: Waiting for Review Submitted: July 30, 2026 at 11:52 AM We opened an App Review Status case on August 10, 2026 and have not received a reply yet. Case ID: 20000133168856 This delay is blocking our planned release and is affecting stakeholder trust in our launch timeline. Could someone from App Review please check whether this submission is stuck in the queue and advise on the current status? Thank you for your help.

I’ve been trying to get this app through App Review for more than two months now. It was rejected a few times before. I changed what Apple asked me to change and submitted it again each time. The current version has now been sitting in Waiting for Review for quite a while and nothing is happening. I’m actually not very familiar with the App Store review process, so I’m not sure how long Waiting for Review is supposed to take. Do I just leave it there and wait? Or should I submit it again? I’m also wondering if I need to create a new submission / new ID at this point. I don’t want to keep changing things if that just sends me back to the beginning of the queue. The whole thing has already been going on for more than two months, so I’m a bit lost on what I’m supposed to do now. Has anyone run into this before?

Hi all, I hope someone from App Review can take a look My situation: QuidProQuote: Memory Keeper (app ID: 6791349683) is a simple cross-platform app where a single purchase unlocks both the macOS and iOS versions. Both versions were submitted from the same build/codebase. The problem is that while my macOS version has been approved and is now pending my release, the iOS version (submission ID: 9fba8d59-d9a7-4a09-bbbe-1d23035adbe1) has been "Waiting for Review" for 12 days now. 2026-07-30, ~4:30pm ET: Both macOS and iOS submissions entered "Waiting for Review" 2026-08-06, ~10am ET: macOS version approved, now Pending Developer Release 2026-08-11 (Today): iOS version still showing "Waiting for Review," 12 days with no status change This ends up being more than a normal wait because the purchase is shared across platforms... releasing the macOS version now would put it in front of customers without the iOS half of what they're paying for. I can't release the approved macOS build until the iOS version clears review, so the delay on one platform is effectively holding both hostage. I did file an expedited review request today (2026-08-11), received confirmation ("we'll expedite this review"). But I read advice that additionally it would be wise to register the problem here. Thanks for any visibility into this!

Hello everyone, I'm facing a frustrating issue with the new App Store Connect UI when trying to submit In-App Purchases alongside my app version. My Situation: App: Nagpur Prime Property (iOS) Rejected under Guideline 2.1(b) — App Completeness Reason: IAPs not submitted with the binary What I've Done: Uploaded new Build 7 (v1.0.1) ✅ Created 2 auto-renewable subscriptions: • Basic Plan (npp_basic_plan) — Ready for Review ✅ • Premium Plan (npp_premium_plan) — Ready for Review ✅ Added both to a Draft Submission (3 items total) ✅ Sandbox tester account added ✅ The Problem: The Draft Submission panel shows: ⚠️ "Unable to Submit for Review — To submit your items for review, add an app version for the selected platform." The "Submit for Review" button is permanently GRAYED OUT. The Draft Submission shows: Versions column: "-" (no app version linked) Items: 3 (Subscription Group + 2 subscriptions) The App Version (Build 7) is in a SEPARATE submission showing "Ready for Review" — but there is NO UI option to link the two submissions together. What I've Tried: Clicking "Add for Review" from Subscription Group page Clicking "Add for Review" from individual plan pages Clicking "Draft Submissions (1)" from version page Contacted Apple Review team — no solution provided Tried "Resubmit to App Review" on version — IAPs not included Question: In Apple's new App Store Connect UI, how do you correctly link an IAP Draft Submission to an App Version submission so they can be reviewed together? Is there a specific order of operations that needs to be followed? Or is there a known workaround for this issue? Thank you in advance!

I understand that they/you are probably being flooded by a lot of AI slop apps or other excuses, but submitting an app 3 weeks ago and it being stuck in Waiting for Review (not first app live on app store either) is beyond a joke. Lodge a support request (not expedited review request) and to get back a generic you will be notified when it changes to In review is not the sort of support help you would expect either. This sort of delay impacts businesses (time and money) and needs to be fixed by either putting more reviewers on - OR better still move more towards the Automated review process Google uses. meantime it still sits there in waiting for review.

Hi everyone, My app just received a rejection citing Guideline 3.1.2(c) - Business - Payments - Subscriptions: "The auto-renewable subscription promotes the free trial, introductory pricing, or introductory period for the subscription more clearly and conspicuously than the billed amount." Does anyone have advice on how to resolve this? I am currently using "Try for Free" as the main CTA button to activate the trial, which seems to be a common industry practice. Any insights would be greatly appreciated!

Hello, This is my first app submission to the App Store. The version has been in "Waiting for Review" for several days and has not yet moved to "In Review". I did replace the build once (to fix a config issue), which I understand restarts the wait. Everything on my side is complete and ready. Is this waiting time normal for a first submission, or should I contact App Review directly? Any guidance on expected timelines would be appreciated. Thank you.

Hello, Our app was submitted on August 7 and has remained in “Waiting for Review” with no status change. This is now a launch-blocking issue for a scheduled enterprise customer rollout on August 13. Hundreds of participants are already scheduled for mobile user testing and are unable to proceed without the iOS app. We have submitted an expedited review request and contacted Developer Support, but have not received a response or any update from either channel. At this point, the App Review delay is directly blocking a committed enterprise launch and participant testing schedule. We would greatly appreciate any urgent assistance in getting this case reviewed or escalated to the appropriate App Review team. App Name: Satellica App Apple ID: 6797731123 Submission ID: b7105850-5a17-489d-907d-550febe3895a Thank you.

Hello, my app was rejected with this reason - Guideline 2.1 - Performance - App Completeness. Bug description: Sign in with Apple requests the Apple ID password rather than entering a code. The issue is that I'm using Clerk inside Expo and they don't support native Apple signIn, only web based. But when users open signIn for the first time - they need to login for appleId via web. I already submitted rejection appeal with explanation. Did someone encounter similar problems? The flow works correctly. In fact even apple testers went through and created accounts.